View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001707K18X001.00 SKB SWANSWpublic2023-04-14 13:162023-04-17 11:32
Reporter(ALTech) Sangmin Choi Assigned To(SW) Jason LingDue Date2023-04-19 14:15
PriorityhighSeveritys4-minorReproducibilityalways
Status closedResolutionfixed 
Summary0001707: The capturing logcat has stopped during standby on/off aging test.
DescriptionHello, Jason,

I'm running standby on/off aging test.
But, the capturing logcat has stopped with following message.

read: unexpected EOF!

I can't get the logcat messages so it's difficult to analyze issues.

Could you please check this issue?
I think the logcat process related with system was died.(logcat -b system)

You can check following steps.

1. Prepare the aging script
adb connect ${IP}
adb root
adb push ai2_standby_on_off_bpm-16746.sh /data

2. Run the aging script
$ adb shell
# chmod 777 /data/ai2_standby_on_off_bpm-16746.sh
# /data/ai2_standby_on_off_bpm-16746.sh

3. Capture the logcat
$ adb shell logcat > logcat.txt

4. Check the logcat process
$ adb shell
# ps -ef | grep logcat
system 1466 1 0 11:47:38 ? 00:00:00 kmsglogd -llogcat
root 1505 1 0 11:47:38 ? 00:00:01 logcat -bmain -f/data/btv_home/tmp/monitor_log/main.log -vthreadtime -r1000 -n1 *:I
root 1508 1 0 11:47:38 ? 00:00:00 logcat -bsystem -f/data/btv_home/tmp/monitor_log/system.log -vthreadtime -r1000 -n1 *:I
shell 5720 389 9 11:51:12 ? 00:00:00 logcat
root 5747 4944 2 11:51:15 pts/2 00:00:00 grep logcat

5. Check the logcat process after 10 minutes
$ adb shell
# ps -ef | grep logcat
system 1466 1 0 11:47:38 ? 00:00:00 kmsglogd -llogcat
root 1505 1 0 11:47:38 ? 00:00:01 logcat -bmain -f/data/btv_home/tmp/monitor_log/main.log -vthreadtime -r1000 -n1 *:I
root 6215 1417 0 11:52:45 ? 00:00:00 sh -c logcat 2>/dev/null
root 6216 6215 0 11:52:45 ? 00:00:00 logcat
root 6250 4944 1 11:52:57 pts/2 00:00:00 grep logcat

6. You can see the "read: unexpected EOF!" message in logcat.txt
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (SW) Jacky Chiang

Activities

(ALTech) Sangmin Choi

2023-04-14 13:16

developer  

ai2_standby_on_off_bpm-16746.sh (486 bytes)    
#!/system/bin/sh
echo 1 > /sys/module/berlin_ir/parameters/protocol
echo 8 > /proc/sys/kernel/printk
ampdiag log on
sleep 3
cat /proc/kmsg | tee /mnt/media_rw/sdcard1/kernel.log &

input keyevent 26; # KEYCODE_POWER;
sleep 10;

while [ 1 ];
do
    # sleep
    input keyevent 26; # KEYCODE_POWER;
    sleep 20;
    input keyevent 20; # KEYCODE_DPAD_DOWN;
    sleep 20;
    input keyevent 26; # KEYCODE_POWER;
    sleep 20;
    input keyevent 20; # KEYCODE_DPAD_DOWN;
    sleep 20;
done&

(ALTech) Sangmin Choi

2023-04-14 13:17

developer   ~0012863

Hi, Jason,

Could you please check this ticket?

Thank you.

(SW) Jason Ling

2023-04-14 13:41

developer   ~0012864

Hi Sangmin,

https://stackoverflow.com/questions/48689930/logcat-crashes-with-error-unexpected-eof

Have you tried to enlarge logcat buffer size?
You can enlarge the logcat buffer before using the logcat command.

logcat -G 20M (You can enlarge more, e.g. logcat -G 100M)

Thanks,
Jason

(ALTech) Sangmin Choi

2023-04-14 14:01

developer   ~0012866

Hi, Jason,

Yes, I increased the logcat buffer size, but the issue still happened.

(SW) Jason Ling

2023-04-14 14:29

developer   ~0012869

Hi Sangmin,

Could you let me know the value you increase? Have you tried larger value ?

Thanks,
Jason

(ALTech) Sangmin Choi

2023-04-14 14:47

developer   ~0012870

Hi, Jason,

I set as 100M but the logcat process didn't use buffer more than 10MiB.
So, I think this issue was not happened due to overflow of logcat buffer.

BFX-UA300:/ $ logcat -g
main: ring buffer is 100 MiB (229 KiB consumed), max entry is 5120 B, max payload is 4068 B
system: ring buffer is 100 MiB (250 KiB consumed), max entry is 5120 B, max payload is 4068 B
crash: ring buffer is 100 MiB (950 B consumed), max entry is 5120 B, max payload is 4068 B

Thank you.
Sangmin Choi.

(ALTech) Sangmin Choi

2023-04-17 11:01

developer   ~0012882

Hi, Jason,

I didn't know the reason why but after factory reset(include reset the authorization of SKB account), this issue was gone.
I close this issue and I will reopen if this issue happens again.

Thank you.
Sangmin Choi.

Issue History

Date Modified Username Field Change
2023-04-14 13:16 (ALTech) Sangmin Choi New Issue
2023-04-14 13:16 (ALTech) Sangmin Choi Status new => assigned
2023-04-14 13:16 (ALTech) Sangmin Choi Assigned To => (SW) Jason Ling
2023-04-14 13:16 (ALTech) Sangmin Choi File Added: ai2_standby_on_off_bpm-16746.sh
2023-04-14 13:17 (ALTech) Sangmin Choi Note Added: 0012863
2023-04-14 13:35 (SW) Jason Ling Issue Monitored: (SW) Jacky Chiang
2023-04-14 13:41 (SW) Jason Ling Note Added: 0012864
2023-04-14 13:41 (SW) Jason Ling Assigned To (SW) Jason Ling => (ALTech) Sangmin Choi
2023-04-14 14:01 (ALTech) Sangmin Choi Note Added: 0012866
2023-04-14 14:02 (ALTech) Sangmin Choi Assigned To (ALTech) Sangmin Choi => (SW) Jason Ling
2023-04-14 14:29 (SW) Jason Ling Note Added: 0012869
2023-04-14 14:47 (ALTech) Sangmin Choi Note Added: 0012870
2023-04-17 11:01 (ALTech) Sangmin Choi Note Added: 0012882
2023-04-17 11:32 (ALTech) Sangmin Choi Status assigned => closed
2023-04-17 11:32 (ALTech) Sangmin Choi Resolution open => fixed